NeXT TypedStream Data | 1995-03-22 | 11.2 KB | 86 lines
typedstream
IBObjectData
Object
CustomObject
WWTCLInterp
Responder
WWColorWell
NXColorWell
Control
)set nuPatch(color) {%f %f %f}; updateView
nuPatch(color)
WWThumbWheel
PAThumbWheel
WWThumbWheelCell
PAThumbWheelCell
ActionCell
Helvetica
&set nuPatch(yTranslate) %f; updateView
nuPatch(yTranslate)
&set nuPatch(zTranslate) %f; updateView
nuPatch(zTranslate)
&set nuPatch(xTranslate) %f; updateView
nuPatch(xTranslate)
WWTextField
TextField
WWTextFieldCell
TextFieldCell
translate
WWSlider
Slider
WWSliderCell
SliderCell
dddf@d@
NXImage
NXCachedImageRep
NXImageRep
iisssssS
iiiiiiS
[2000c]
"set nuPatch(xScale) %f; updateView
nuPatch(xScale)
-10.00
"set nuPatch(yScale) %f; updateView
nuPatch(yScale)
"set nuPatch(zScale) %f; updateView
nuPatch(zScale)
scale
ScrollView
ClipView
ciifffcfffs
[1509c]{\rtf0\ansi{\fonttbl\f0\fswiss Helvetica;}
\margl40
\margr40
\pard\tx520\tx1060\tx1600\tx2120\tx2660\tx3200\tx3720\tx4260\tx4800\tx5320\f0\b0\i0\ulnone\fs24\fc0\cf0 Note that this non-uniform rational b-spline (NURBS) surface seems really coarse. To see what I mean, use prman to render it - it looks like a box when qrman renders it, but a really nice cylinder when prman renders it. Also notice that the "QR" subpanel of the "C" part of the WW3DWell control panel has no effect on it. Weird, huh?\
The problem is that the tesselations values that you pass in to qrman are totally inappropriate for things other than NURBS. In other words, if you use values of (16,16) (the default "nice" value in the WW3DWell), you would get a NURBS surface that would take forever to render on most NEXTSTEP boxes. In other words, a low value (say 1 to 4) does a reasonable job for your average complexity NURBS surface you get from (say) Alias, but give you a really bad quadric. \
So, as a somewhat lame workaround, all RIBNuPatch objects do a \